Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91ca3a969c72c9016a774c7b764ecda4e95e965909f10cd983f3e10ece62d36b

Tx prefix hash: a51685fe00df29b89ae18b3d3c7c312c925e1e77c1d6b148d35f882799f48ed4
Tx public key: 8bfd55b5d1ed19bd31696b3d85e4f1e97578e2ebd5513c96963c6b19a82ece2e
Timestamp: 1737245785 Timestamp [UCT]: 2025-01-19 00:16:25 Age [y:d:h:m:s]: 00:053:03:38:06
Block: 1200347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37803 RingCT/type: yes/0
Extra: 018bfd55b5d1ed19bd31696b3d85e4f1e97578e2ebd5513c96963c6b19a82ece2e021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac80fa6688a63b1dd065ae6fb8855e5cf196b0a3d0cbeb90d01a5d61ead5c2ee 0.600000000000 1686990 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": 1200357, "vin": [ { "gen": { "height": 1200347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac80fa6688a63b1dd065ae6fb8855e5cf196b0a3d0cbeb90d01a5d61ead5c2ee" } } ], "extra": [ 1, 139, 253, 85, 181, 209, 237, 25, 189, 49, 105, 107, 61, 133, 228, 241, 233, 117, 120, 226, 235, 213, 81, 60, 150, 150, 60, 107, 25, 168, 46, 206, 46, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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