Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4284b54a541337f1b95454640b512504bbf7aee7b177f5787c7e7b20ace0b209

Tx prefix hash: cf584fe298d908fdb1aa368a4fa1bbda143f8b49c1342d61d019ff8648b5f4f2
Tx public key: 502b7efb4484b6a88413ee683c4a6ad91fd42c9063208c647ec798e9f8767a52
Timestamp: 1714920351 Timestamp [UCT]: 2024-05-05 14:45:51 Age [y:d:h:m:s]: 00:248:03:13:14
Block: 1015456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177585 RingCT/type: yes/0
Extra: 01502b7efb4484b6a88413ee683c4a6ad91fd42c9063208c647ec798e9f8767a5202110000000d0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9f144ea7995a314f6e60b8d639fe12dd8b74942f917f18ec8a8faf089acc047 0.600000000000 1478825 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": 1015466, "vin": [ { "gen": { "height": 1015456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9f144ea7995a314f6e60b8d639fe12dd8b74942f917f18ec8a8faf089acc047" } } ], "extra": [ 1, 80, 43, 126, 251, 68, 132, 182, 168, 132, 19, 238, 104, 60, 74, 106, 217, 31, 212, 44, 144, 99, 32, 140, 100, 126, 199, 152, 233, 248, 118, 122, 82, 2, 17, 0, 0, 0, 13, 0, 17, 5, 91, 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