Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d789b6aadf585380efe5216485d4a33cab28778e392d0c7541fe05618eaf9d94

Tx prefix hash: 56e6de17284e3331086c5b54be2024eac21bad8658f9576f7e4579c38f9796fd
Tx public key: 90fd3a2a7c80b7f231162cf562a18a7c26b3458792e957460317183a950795aa
Timestamp: 1720494352 Timestamp [UCT]: 2024-07-09 03:05:52 Age [y:d:h:m:s]: 00:267:05:57:37
Block: 1061664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190918 RingCT/type: yes/0
Extra: 0190fd3a2a7c80b7f231162cf562a18a7c26b3458792e957460317183a950795aa02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9630614e2ce5a8a28fb33628d2d17c04cb2d468d41e6eef165753b5e72dc64a0 0.600000000000 1532157 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": 1061674, "vin": [ { "gen": { "height": 1061664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9630614e2ce5a8a28fb33628d2d17c04cb2d468d41e6eef165753b5e72dc64a0" } } ], "extra": [ 1, 144, 253, 58, 42, 124, 128, 183, 242, 49, 22, 44, 245, 98, 161, 138, 124, 38, 179, 69, 135, 146, 233, 87, 70, 3, 23, 24, 58, 149, 7, 149, 170, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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