Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c54890238a69ed44adea664a8a3df6364a3f3ed4753de7ea596d7263e3092971

Tx prefix hash: 25a375e13b7fa75db3139a3d598f4ffaaa297a7fc3a28dec0fe6bff8a104174b
Tx public key: e9522401c15ac43444e48e0ee9b10588c07b8cdff0df0020d31e99d2435d6efb
Timestamp: 1704772604 Timestamp [UCT]: 2024-01-09 03:56:44 Age [y:d:h:m:s]: 01:157:00:23:52
Block: 931283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373308 RingCT/type: yes/0
Extra: 01e9522401c15ac43444e48e0ee9b10588c07b8cdff0df0020d31e99d2435d6efb02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c46945d3a4857d6db666f58740c2cf9131f14f69f2b06f3ccd92b5c89fbf0b70 0.600000000000 1389179 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": 931293, "vin": [ { "gen": { "height": 931283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c46945d3a4857d6db666f58740c2cf9131f14f69f2b06f3ccd92b5c89fbf0b70" } } ], "extra": [ 1, 233, 82, 36, 1, 193, 90, 196, 52, 68, 228, 142, 14, 233, 177, 5, 136, 192, 123, 140, 223, 240, 223, 0, 32, 211, 30, 153, 210, 67, 93, 110, 251, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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