Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1dad36d47d3c25ebaeced3620ca8048a7e4eb83a61881126307ea6ce9b4aa08

Tx prefix hash: f267acabd700fecbb57948495178f3e5c41b2d54f34861ba9efa94cabace5c3a
Tx public key: d9731031ae7b607028c8e39e9ea1b9bb4ea9dc22bfae64256edf8b05ab312df8
Timestamp: 1732547779 Timestamp [UCT]: 2024-11-25 15:16:19 Age [y:d:h:m:s]: 00:135:01:08:10
Block: 1161482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96328 RingCT/type: yes/0
Extra: 01d9731031ae7b607028c8e39e9ea1b9bb4ea9dc22bfae64256edf8b05ab312df802110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55e74bd9adb54e0f4a6fb2732df4d0914ffc5a2c75dd042614f44ca9a7d2ea59 0.600000000000 1647137 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": 1161492, "vin": [ { "gen": { "height": 1161482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55e74bd9adb54e0f4a6fb2732df4d0914ffc5a2c75dd042614f44ca9a7d2ea59" } } ], "extra": [ 1, 217, 115, 16, 49, 174, 123, 96, 112, 40, 200, 227, 158, 158, 161, 185, 187, 78, 169, 220, 34, 191, 174, 100, 37, 110, 223, 139, 5, 171, 49, 45, 248, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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