Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e1b7d1526cc8a0a2fd8724d07661bccef27dc6ab55401e9935b6188a8cf80f4

Tx prefix hash: 596d78567b6af23c4a442c872cda3acf3b934beb7866a8a53978aef0cd18bc16
Tx public key: a017d5e89bfe6683eb5e4ac636fee58d69949db6adb9f72523cace0616cdcb89
Timestamp: 1729708604 Timestamp [UCT]: 2024-10-23 18:36:44 Age [y:d:h:m:s]: 00:160:06:55:10
Block: 1138013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114340 RingCT/type: yes/0
Extra: 01a017d5e89bfe6683eb5e4ac636fee58d69949db6adb9f72523cace0616cdcb890211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d2818cb39013e09a924de7550d6d59d8349d3631cc42d38d051fd920d4f946a 0.600000000000 1621612 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": 1138023, "vin": [ { "gen": { "height": 1138013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d2818cb39013e09a924de7550d6d59d8349d3631cc42d38d051fd920d4f946a" } } ], "extra": [ 1, 160, 23, 213, 232, 155, 254, 102, 131, 235, 94, 74, 198, 54, 254, 229, 141, 105, 148, 157, 182, 173, 185, 247, 37, 35, 202, 206, 6, 22, 205, 203, 137, 2, 17, 0, 0, 0, 4, 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