Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1ee4f084959d5f4325c4352c6788026e35227dfd509138a42c07fc5bc93968b

Tx prefix hash: 50422a0fba42960dc2df9f6b0177ff315a896d783ba3d0ff93e8caba46e06444
Tx public key: 7be7be2ed570a93d282d14db2c01aae0fdbb2d0d163802f66ffb8c0d6e20e804
Timestamp: 1709138261 Timestamp [UCT]: 2024-02-28 16:37:41 Age [y:d:h:m:s]: 01:109:15:22:24
Block: 967518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339296 RingCT/type: yes/0
Extra: 017be7be2ed570a93d282d14db2c01aae0fdbb2d0d163802f66ffb8c0d6e20e80402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bafd7ec037775e95fbd808b8bbe12cce56e2c103fa3cc9a4c9d8c2cda9852624 0.600000000000 1427299 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": 967528, "vin": [ { "gen": { "height": 967518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bafd7ec037775e95fbd808b8bbe12cce56e2c103fa3cc9a4c9d8c2cda9852624" } } ], "extra": [ 1, 123, 231, 190, 46, 213, 112, 169, 61, 40, 45, 20, 219, 44, 1, 170, 224, 253, 187, 45, 13, 22, 56, 2, 246, 111, 251, 140, 13, 110, 32, 232, 4, 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