Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67efc9c6da347f87adb4b8b632a8ceb2f2419798b9c66074289700a543019288

Tx prefix hash: c2034489ca7f3f3e13c41e0be54647a9fe6ec4464645740d846370234072ae04
Tx public key: 02b20edaee3bc1e49e9d4e1b393dd5d76165cd4e8e7b59bdca80392212970b88
Timestamp: 1583851913 Timestamp [UCT]: 2020-03-10 14:51:53 Age [y:d:h:m:s]: 05:084:00:04:07
Block: 79815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1215884 RingCT/type: yes/0
Extra: 0102b20edaee3bc1e49e9d4e1b393dd5d76165cd4e8e7b59bdca80392212970b88021100000006c48ea382000000000000000000

1 output(s) for total of 333.841684009000 dcy

stealth address amount amount idx
00: dd158b6d85cb4d65ef848e953a3d67c73104c367ed897e0ef5a176aaf2ae7e06 333.841684009000 146039 of 0

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": 79825, "vin": [ { "gen": { "height": 79815 } } ], "vout": [ { "amount": 333841684009, "target": { "key": "dd158b6d85cb4d65ef848e953a3d67c73104c367ed897e0ef5a176aaf2ae7e06" } } ], "extra": [ 1, 2, 178, 14, 218, 238, 59, 193, 228, 158, 157, 78, 27, 57, 61, 213, 215, 97, 101, 205, 78, 142, 123, 89, 189, 202, 128, 57, 34, 18, 151, 11, 136, 2, 17, 0, 0, 0, 6, 196, 142, 163, 130, 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