Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95c39b98ea49d065422dfd899ff61f7fefe050570488df61d031c2f294f2f174

Tx prefix hash: cca23fd3c9770639b6f20aa283a178701c98b830c6bb326da5f009c671838cc4
Tx public key: 813cdb7bb21753e93ff9b40a8d1300535bbe7bcedb57fbf83e0914bf66fd212e
Timestamp: 1673754925 Timestamp [UCT]: 2023-01-15 03:55:25 Age [y:d:h:m:s]: 02:298:21:10:01
Block: 675021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 732998 RingCT/type: yes/0
Extra: 01813cdb7bb21753e93ff9b40a8d1300535bbe7bcedb57fbf83e0914bf66fd212e0211000000018b7b6602000000000000000000

1 output(s) for total of 3.559386610000 dcy

stealth address amount amount idx
00: 0f66081a1743005c5aa306b342f88b8d7e05f23a7845cfda2894b3863ef1f649 3.559386610000 1116686 of 0

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": 675031, "vin": [ { "gen": { "height": 675021 } } ], "vout": [ { "amount": 3559386610, "target": { "key": "0f66081a1743005c5aa306b342f88b8d7e05f23a7845cfda2894b3863ef1f649" } } ], "extra": [ 1, 129, 60, 219, 123, 178, 23, 83, 233, 63, 249, 180, 10, 141, 19, 0, 83, 91, 190, 123, 206, 219, 87, 251, 248, 62, 9, 20, 191, 102, 253, 33, 46, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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