Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4b468fd031655a642eb7cac45083e8bc4b170c3ea4f8d52680cd08996a0aa65

Tx prefix hash: 7d438eaa806a3005c3c7ff1f72d5721307f910027a97ba0f81fa3c818aa3b435
Tx public key: c4892b363822b24d9289eaed527db16c7d86a72ed9a01b21135c1853c922d6e4
Timestamp: 1726786148 Timestamp [UCT]: 2024-09-19 22:49:08 Age [y:d:h:m:s]: 00:268:14:14:28
Block: 1113813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191730 RingCT/type: yes/0
Extra: 01c4892b363822b24d9289eaed527db16c7d86a72ed9a01b21135c1853c922d6e402110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 770aa9477742823c3bad145f009387e1394f38b62fe512f674e29bd8d85126b9 0.600000000000 1593610 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": 1113823, "vin": [ { "gen": { "height": 1113813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "770aa9477742823c3bad145f009387e1394f38b62fe512f674e29bd8d85126b9" } } ], "extra": [ 1, 196, 137, 43, 54, 56, 34, 178, 77, 146, 137, 234, 237, 82, 125, 177, 108, 125, 134, 167, 46, 217, 160, 27, 33, 19, 92, 24, 83, 201, 34, 214, 228, 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