Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0837ca696271f33de501ce80a8905c49607706549e4e50636b7ad57a3a41414d

Tx prefix hash: 682bff35c049f71d72aabb0e674bcd6f086855bd0c2e1f7da93dfd16fef35a6a
Tx public key: ea5033a6e29266c8e6b74aa39c8629186b973bf8354efe5a1f3d5e6068a4e1e0
Timestamp: 1694882169 Timestamp [UCT]: 2023-09-16 16:36:09 Age [y:d:h:m:s]: 01:238:17:07:02
Block: 849497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431724 RingCT/type: yes/0
Extra: 01ea5033a6e29266c8e6b74aa39c8629186b973bf8354efe5a1f3d5e6068a4e1e002110000000175e3f0e9000000000000000000

1 output(s) for total of 0.940294408000 dcy

stealth address amount amount idx
00: 5e91e397315c781a5cf5124d80e42ce01cc3bf9edbb39e4eea584279121f8844 0.940294408000 1303165 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": 849507, "vin": [ { "gen": { "height": 849497 } } ], "vout": [ { "amount": 940294408, "target": { "key": "5e91e397315c781a5cf5124d80e42ce01cc3bf9edbb39e4eea584279121f8844" } } ], "extra": [ 1, 234, 80, 51, 166, 226, 146, 102, 200, 230, 183, 74, 163, 156, 134, 41, 24, 107, 151, 59, 248, 53, 78, 254, 90, 31, 61, 94, 96, 104, 164, 225, 224, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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