Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5400903972f40c0a870e2354c1fe5e659777f11d2b8ebf051ced697b5d8a0a6b

Tx prefix hash: 0b126ec5aad0b632ef4784106a1e4ad659c47d6801d2ecaab0bc9ae3d2cd38a8
Tx public key: ab50bdf7923b11e95c6f69e5cf60751aef7e3a6bccc48d05207a1743582de1c3
Timestamp: 1736181203 Timestamp [UCT]: 2025-01-06 16:33:23 Age [y:d:h:m:s]: 00:154:14:08:46
Block: 1191584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110302 RingCT/type: yes/0
Extra: 01ab50bdf7923b11e95c6f69e5cf60751aef7e3a6bccc48d05207a1743582de1c30211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9c501920ff91a925866c8cf0a4dc39f7afab2371fb92999b82fbd3136ea1398 0.600000000000 1678123 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": 1191594, "vin": [ { "gen": { "height": 1191584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9c501920ff91a925866c8cf0a4dc39f7afab2371fb92999b82fbd3136ea1398" } } ], "extra": [ 1, 171, 80, 189, 247, 146, 59, 17, 233, 92, 111, 105, 229, 207, 96, 117, 26, 239, 126, 58, 107, 204, 196, 141, 5, 32, 122, 23, 67, 88, 45, 225, 195, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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