Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b620e7cb9dd70e844f2780d44e0b734cb3fadbdd4496d43a482a6d6cc541179

Tx prefix hash: 47ced94ff8978110134d9aa4df606c984665bd42615b9d10cb98a443e57827cf
Tx public key: 0936f1b26608e4de9b945d27d5edb43188df6e53d2e51db329e34af90a11cc8d
Timestamp: 1725856516 Timestamp [UCT]: 2024-09-09 04:35:16 Age [y:d:h:m:s]: 00:124:15:15:12
Block: 1106109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89122 RingCT/type: yes/0
Extra: 010936f1b26608e4de9b945d27d5edb43188df6e53d2e51db329e34af90a11cc8d02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1175b5544aaf5200c469605d7cb583a87d380c5ed4aa2b7fed74610ba87fd77 0.600000000000 1583686 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": 1106119, "vin": [ { "gen": { "height": 1106109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1175b5544aaf5200c469605d7cb583a87d380c5ed4aa2b7fed74610ba87fd77" } } ], "extra": [ 1, 9, 54, 241, 178, 102, 8, 228, 222, 155, 148, 93, 39, 213, 237, 180, 49, 136, 223, 110, 83, 210, 229, 29, 179, 41, 227, 74, 249, 10, 17, 204, 141, 2, 17, 0, 0, 0, 3, 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