Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b9787134bd2b67c37c64ef469fcc64b42076ef6b26998730d9c6b04b7f85ca0

Tx prefix hash: ee074afd14653b83095baa3d6cce6ef5ddc89ddced24d27744c0e383feaa402e
Tx public key: 1bf4f3a8c4d8bda5da057ae7c3d2bce4be1114cc83bbb66ae937096d2f1f8f2c
Timestamp: 1706801527 Timestamp [UCT]: 2024-02-01 15:32:07 Age [y:d:h:m:s]: 01:065:11:52:49
Block: 948117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307867 RingCT/type: yes/0
Extra: 011bf4f3a8c4d8bda5da057ae7c3d2bce4be1114cc83bbb66ae937096d2f1f8f2c0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b66f7351c5c022b5676615b986ba9d88586e133d12125609e61955ed70d39c58 0.600000000000 1406489 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": 948127, "vin": [ { "gen": { "height": 948117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b66f7351c5c022b5676615b986ba9d88586e133d12125609e61955ed70d39c58" } } ], "extra": [ 1, 27, 244, 243, 168, 196, 216, 189, 165, 218, 5, 122, 231, 195, 210, 188, 228, 190, 17, 20, 204, 131, 187, 182, 106, 233, 55, 9, 109, 47, 31, 143, 44, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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