Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 981a4f1760c390f562fbfeaaf757614939c1dc78ca49a699e79fd0ae69658143

Tx prefix hash: adda623a0db4fa4760da9fbe5783ec56b54a2ab4fb64b5db068190418791fb4a
Tx public key: e46bc46cfe3b31288cd3ccff5cf5b7d495b94d9c6dad398ea160bc174db20bf3
Timestamp: 1726086422 Timestamp [UCT]: 2024-09-11 20:27:02 Age [y:d:h:m:s]: 00:233:18:42:32
Block: 1108011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166933 RingCT/type: yes/0
Extra: 01e46bc46cfe3b31288cd3ccff5cf5b7d495b94d9c6dad398ea160bc174db20bf3021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7de52594f763e3a7f3d0b026f82c36ae4012d0623faf5bceba431d77e04d9748 0.600000000000 1585754 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": 1108021, "vin": [ { "gen": { "height": 1108011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7de52594f763e3a7f3d0b026f82c36ae4012d0623faf5bceba431d77e04d9748" } } ], "extra": [ 1, 228, 107, 196, 108, 254, 59, 49, 40, 140, 211, 204, 255, 92, 245, 183, 212, 149, 185, 77, 156, 109, 173, 57, 142, 161, 96, 188, 23, 77, 178, 11, 243, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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