Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a53d12f55cf59060d66d4c04495e8f9a7a66d746ad47f3851a587fcb3bc16a30

Tx prefix hash: 8e1c45a199634fb024f9bb7e156876f0f66b49f52ffa0eaa299a2d2f640bbbf1
Tx public key: 9cb4cd472ec81f78de8ecb514e55b66d90e0e6179993929f6c07ebae402285fc
Timestamp: 1639181072 Timestamp [UCT]: 2021-12-11 00:04:32 Age [y:d:h:m:s]: 02:353:04:26:59
Block: 392828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 770485 RingCT/type: yes/0
Extra: 019cb4cd472ec81f78de8ecb514e55b66d90e0e6179993929f6c07ebae402285fc0211000000b6e9564d6f000000000000000000

1 output(s) for total of 30.647716897000 dcy

stealth address amount amount idx
00: f79bc2c6044ee76273d7e3b05f5d533dd9fb2010cb5a34dd883aeec836d08049 30.647716897000 789837 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": 392838, "vin": [ { "gen": { "height": 392828 } } ], "vout": [ { "amount": 30647716897, "target": { "key": "f79bc2c6044ee76273d7e3b05f5d533dd9fb2010cb5a34dd883aeec836d08049" } } ], "extra": [ 1, 156, 180, 205, 71, 46, 200, 31, 120, 222, 142, 203, 81, 78, 85, 182, 109, 144, 224, 230, 23, 153, 147, 146, 159, 108, 7, 235, 174, 64, 34, 133, 252, 2, 17, 0, 0, 0, 182, 233, 86, 77, 111, 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