Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6ea31b6702b25036552a7ea109d6eadaca20e47c446ca005a8eba7cab9be1a8

Tx prefix hash: 20aba2107df29fdb0404c3853d2ceeb3762e40f683efc775c4440347ab923fb3
Tx public key: 786d6fcf9d50decf02892066a4fdc4d7d6e2574691cbc51c89385f28f473a1da
Timestamp: 1731524946 Timestamp [UCT]: 2024-11-13 19:09:06 Age [y:d:h:m:s]: 00:010:10:27:49
Block: 1153014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7465 RingCT/type: yes/0
Extra: 01786d6fcf9d50decf02892066a4fdc4d7d6e2574691cbc51c89385f28f473a1da021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39578ac8145bb9a97bfa099a7c166338dffa55f1e0cf2c007ac3a50cd9f94236 0.600000000000 1638621 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": 1153024, "vin": [ { "gen": { "height": 1153014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39578ac8145bb9a97bfa099a7c166338dffa55f1e0cf2c007ac3a50cd9f94236" } } ], "extra": [ 1, 120, 109, 111, 207, 157, 80, 222, 207, 2, 137, 32, 102, 164, 253, 196, 215, 214, 226, 87, 70, 145, 203, 197, 28, 137, 56, 95, 40, 244, 115, 161, 218, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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