Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bad5660b4cdec15f55de1e6c88e61472cc3cbef100cd25ffce76d80b930e7d40

Tx prefix hash: dbb58983d1014a7d9029623bd21b3f01cc092849fb47ea56759e7a0783f740b0
Tx public key: 697a4186d0f4c069f684987459c5eb7f5ffa3198fa310928b3e233f1b9cb96fe
Timestamp: 1652265858 Timestamp [UCT]: 2022-05-11 10:44:18 Age [y:d:h:m:s]: 03:174:08:54:56
Block: 498660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 903482 RingCT/type: yes/0
Extra: 01697a4186d0f4c069f684987459c5eb7f5ffa3198fa310928b3e233f1b9cb96fe0211000000042e6b1fd5000000000000000000

1 output(s) for total of 13.668870339000 dcy

stealth address amount amount idx
00: 7f5cbc21e5e6855c2427d798a3d9f09b2200b0f574b5c08e01139bfff07805b7 13.668870339000 922869 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 498670, "vin": [ { "gen": { "height": 498660 } } ], "vout": [ { "amount": 13668870339, "target": { "key": "7f5cbc21e5e6855c2427d798a3d9f09b2200b0f574b5c08e01139bfff07805b7" } } ], "extra": [ 1, 105, 122, 65, 134, 208, 244, 192, 105, 246, 132, 152, 116, 89, 197, 235, 127, 95, 250, 49, 152, 250, 49, 9, 40, 179, 226, 51, 241, 185, 203, 150, 254, 2, 17, 0, 0, 0, 4, 46, 107, 31, 213, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8