Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f5ec84ca10d78806527a99730dc539c5e3d96c4b42cc1fd0246de1ef3900db6

Tx prefix hash: 5b78d05bf8b8ac7ef25b5e6bbe01b9fa066cd90376e8fea42f1b2302df1b4454
Tx public key: 3e91d02f4e30f63935e9e2de5ad95be715863b23ce2e6785fdd0695450df77ce
Timestamp: 1735375483 Timestamp [UCT]: 2024-12-28 08:44:43 Age [y:d:h:m:s]: 00:099:14:34:56
Block: 1184900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70961 RingCT/type: yes/0
Extra: 013e91d02f4e30f63935e9e2de5ad95be715863b23ce2e6785fdd0695450df77ce0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c08c9f70cf7a299e7e104a41a04bd5153e2772607b01a88945bb417eef248af 0.600000000000 1671363 of 15

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": 1184910, "vin": [ { "gen": { "height": 1184900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c08c9f70cf7a299e7e104a41a04bd5153e2772607b01a88945bb417eef248af" } } ], "extra": [ 1, 62, 145, 208, 47, 78, 48, 246, 57, 53, 233, 226, 222, 90, 217, 91, 231, 21, 134, 59, 35, 206, 46, 103, 133, 253, 208, 105, 84, 80, 223, 119, 206, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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