Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37000dffc92443633d9b3ed9f5c28346a5dd84672e14ddc087081b32bcb417a0

Tx prefix hash: 2cebbd841bc76c9aad5e39c63c558218eb0f6361ce4dc4776521fb953432a0cf
Tx public key: ca170d717c2073274d04678efa6491c954ac3a95b1ab847a4f7ae12a1e4f11c7
Timestamp: 1724573908 Timestamp [UCT]: 2024-08-25 08:18:28 Age [y:d:h:m:s]: 01:071:06:51:55
Block: 1095469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309394 RingCT/type: yes/0
Extra: 01ca170d717c2073274d04678efa6491c954ac3a95b1ab847a4f7ae12a1e4f11c702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c72736fd5dec47a810241b4556dbbf4fa7a14e523a0e0ba5592765948182bf10 0.600000000000 1570646 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": 1095479, "vin": [ { "gen": { "height": 1095469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c72736fd5dec47a810241b4556dbbf4fa7a14e523a0e0ba5592765948182bf10" } } ], "extra": [ 1, 202, 23, 13, 113, 124, 32, 115, 39, 77, 4, 103, 142, 250, 100, 145, 201, 84, 172, 58, 149, 177, 171, 132, 122, 79, 122, 225, 42, 30, 79, 17, 199, 2, 17, 0, 0, 0, 5, 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