Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0538f96f1887e86af553bf1e06ad53e99ca1ffc90d6f5c80e8682c3a9f5cd4bb

Tx prefix hash: 0f7dfc14b4fb5e189473c939a2591c666f007318c3f1bdb0e35f13b2a0fee7fd
Tx public key: f7878560196952e300c55c4b1374f316920b556197d46c7eb3b1ec72f2216c24
Timestamp: 1701127573 Timestamp [UCT]: 2023-11-27 23:26:13 Age [y:d:h:m:s]: 01:346:02:22:01
Block: 901101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506231 RingCT/type: yes/0
Extra: 01f7878560196952e300c55c4b1374f316920b556197d46c7eb3b1ec72f2216c2402110000000575e3f0e9000000000000000000

1 output(s) for total of 0.634276037000 dcy

stealth address amount amount idx
00: d692326e1adb7772fa9b5f8d7c10a7948e3b962f6c80d3dfafe57a85db256a9c 0.634276037000 1357632 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": 901111, "vin": [ { "gen": { "height": 901101 } } ], "vout": [ { "amount": 634276037, "target": { "key": "d692326e1adb7772fa9b5f8d7c10a7948e3b962f6c80d3dfafe57a85db256a9c" } } ], "extra": [ 1, 247, 135, 133, 96, 25, 105, 82, 227, 0, 197, 92, 75, 19, 116, 243, 22, 146, 11, 85, 97, 151, 212, 108, 126, 179, 177, 236, 114, 242, 33, 108, 36, 2, 17, 0, 0, 0, 5, 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