Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f611d9011c22ece4ca8b718325ab71e94c53751a4d786785d6e69bede45790d

Tx prefix hash: 25c78bb939a583f0de4854e8930ca1595d718ab3f4c8194dc96804878dae9f5f
Tx public key: 35b16498e12b8e26cb1294f86de691a225f9a0c2f8c5b87627da874695b27664
Timestamp: 1713999491 Timestamp [UCT]: 2024-04-24 22:58:11 Age [y:d:h:m:s]: 00:259:12:55:55
Block: 1007805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185774 RingCT/type: yes/0
Extra: 0135b16498e12b8e26cb1294f86de691a225f9a0c2f8c5b87627da874695b2766402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64bb452be9ff525b980c14b7a7bd7f59e34d40a4caa2979fb3a82a69a55fc4c8 0.600000000000 1469263 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": 1007815, "vin": [ { "gen": { "height": 1007805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64bb452be9ff525b980c14b7a7bd7f59e34d40a4caa2979fb3a82a69a55fc4c8" } } ], "extra": [ 1, 53, 177, 100, 152, 225, 43, 142, 38, 203, 18, 148, 248, 109, 230, 145, 162, 37, 249, 160, 194, 248, 197, 184, 118, 39, 218, 135, 70, 149, 178, 118, 100, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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