Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1bb746d02cd09f143513d7d537447519b4da5f64105d4172cd7ee7f86414db0

Tx prefix hash: c6a2bc684c84d389015f25f0226355e7da61a33b69cbdb1d8fc3d585f7597a0a
Tx public key: e6d8fe4c767d9e48b3794e8738e98ac019a516a4cf9e09710a18c056f879c960
Timestamp: 1694868226 Timestamp [UCT]: 2023-09-16 12:43:46 Age [y:d:h:m:s]: 01:162:14:35:01
Block: 849391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377263 RingCT/type: yes/0
Extra: 01e6d8fe4c767d9e48b3794e8738e98ac019a516a4cf9e09710a18c056f879c960021100000003faf35c9c000000000000000000

1 output(s) for total of 0.941055150000 dcy

stealth address amount amount idx
00: ad3d85f780d5761c6d7bf47b3ccc62483bf25c6b7570a2eb0c04af87ae842e8d 0.941055150000 1303055 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": 849401, "vin": [ { "gen": { "height": 849391 } } ], "vout": [ { "amount": 941055150, "target": { "key": "ad3d85f780d5761c6d7bf47b3ccc62483bf25c6b7570a2eb0c04af87ae842e8d" } } ], "extra": [ 1, 230, 216, 254, 76, 118, 125, 158, 72, 179, 121, 78, 135, 56, 233, 138, 192, 25, 165, 22, 164, 207, 158, 9, 113, 10, 24, 192, 86, 248, 121, 201, 96, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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