Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 361e5aff3b2cad3880c993d86523168258d8a4d944e872cb4727437581225333

Tx prefix hash: bbf96d6a7661e632d81ee4f11dc097af8bbfe039aeaf29465390267bbb88052d
Tx public key: 4eaa74991c156798b3c700768c3963dfe8f5cbdf5b70ea0f1d404df9b359823d
Timestamp: 1706774356 Timestamp [UCT]: 2024-02-01 07:59:16 Age [y:d:h:m:s]: 01:028:20:22:59
Block: 947891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281659 RingCT/type: yes/0
Extra: 014eaa74991c156798b3c700768c3963dfe8f5cbdf5b70ea0f1d404df9b359823d021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 482decf34fb189089638a456af8f88e8981fbf52e0c8ec49c142b58cd38db6e7 0.600000000000 1406251 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": 947901, "vin": [ { "gen": { "height": 947891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "482decf34fb189089638a456af8f88e8981fbf52e0c8ec49c142b58cd38db6e7" } } ], "extra": [ 1, 78, 170, 116, 153, 28, 21, 103, 152, 179, 199, 0, 118, 140, 57, 99, 223, 232, 245, 203, 223, 91, 112, 234, 15, 29, 64, 77, 249, 179, 89, 130, 61, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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