Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5478b46ae75c8716ae06aedef16ec904c113eadc0625a5890584a180f46364c

Tx prefix hash: b37a6808d1a8bd01e1640ea9600a898d9abac7ce8770f15ab6e233a720d7d6c7
Tx public key: c4781d7ba80f01579a070630341eda6ac1b388fb8c8a2c4ab325ae026fe8a467
Timestamp: 1720212207 Timestamp [UCT]: 2024-07-05 20:43:27 Age [y:d:h:m:s]: 01:137:11:39:36
Block: 1059309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356805 RingCT/type: yes/0
Extra: 01c4781d7ba80f01579a070630341eda6ac1b388fb8c8a2c4ab325ae026fe8a4670211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17ced31359fa52a1883ab9467b2ebd17dedfd0df307af06181ae9e4fad64e1f4 0.600000000000 1529776 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": 1059319, "vin": [ { "gen": { "height": 1059309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17ced31359fa52a1883ab9467b2ebd17dedfd0df307af06181ae9e4fad64e1f4" } } ], "extra": [ 1, 196, 120, 29, 123, 168, 15, 1, 87, 154, 7, 6, 48, 52, 30, 218, 106, 193, 179, 136, 251, 140, 138, 44, 74, 179, 37, 174, 2, 111, 232, 164, 103, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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