Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0acbb33ba594cb81921bffc3abc196283d249d5b70daa0965ef2d1e0b82fc798

Tx prefix hash: 36c8bfc575c67b4d7cb1e19c5b801ed35683487327d3258e24d2c2d1dc609468
Tx public key: 3eab4a3f178ddd54b9e62ba62910aaeb1cc057a684a9fb6f7cec7360f89b2d7a
Timestamp: 1728945120 Timestamp [UCT]: 2024-10-14 22:32:00 Age [y:d:h:m:s]: 00:167:15:11:35
Block: 1131717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119580 RingCT/type: yes/0
Extra: 013eab4a3f178ddd54b9e62ba62910aaeb1cc057a684a9fb6f7cec7360f89b2d7a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23c9a4d1f23484986f4215165815a1167b08ae42a2fc50a8143afb92ddaeae65 0.600000000000 1614622 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": 1131727, "vin": [ { "gen": { "height": 1131717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23c9a4d1f23484986f4215165815a1167b08ae42a2fc50a8143afb92ddaeae65" } } ], "extra": [ 1, 62, 171, 74, 63, 23, 141, 221, 84, 185, 230, 43, 166, 41, 16, 170, 235, 28, 192, 87, 166, 132, 169, 251, 111, 124, 236, 115, 96, 248, 155, 45, 122, 2, 17, 0, 0, 0, 4, 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