Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa46d9a65479b27899db2f8d76d35fcdbe2b503cbc4d4f248e18a46463fead2f

Tx prefix hash: 5fd8274a32bee6169a52ea76a755dc93f4c40467e1cc9f7ae9465256d6c5d562
Tx public key: c9dc294abd9de23b108834b63b35126c76d721ab615c4b785eddc012735e8d10
Timestamp: 1717546176 Timestamp [UCT]: 2024-06-05 00:09:36 Age [y:d:h:m:s]: 01:195:07:23:23
Block: 1037218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398199 RingCT/type: yes/0
Extra: 01c9dc294abd9de23b108834b63b35126c76d721ab615c4b785eddc012735e8d1002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dfe396efee76dee5d66922856450896177d835e1d2af90f4ba5ad8844b5819d 0.600000000000 1505749 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": 1037228, "vin": [ { "gen": { "height": 1037218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dfe396efee76dee5d66922856450896177d835e1d2af90f4ba5ad8844b5819d" } } ], "extra": [ 1, 201, 220, 41, 74, 189, 157, 226, 59, 16, 136, 52, 182, 59, 53, 18, 108, 118, 215, 33, 171, 97, 92, 75, 120, 94, 221, 192, 18, 115, 94, 141, 16, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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