Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7811edfc2d26d175679f6865531915907542efc1c72a699523432bc60261e23

Tx prefix hash: 6f420dc14d5cc28094f4789b9301d11875cdb1c1fbc35066baf7847dda4120d8
Tx public key: 4f960992d089fa9e35dfb8f1d992697f9ce8eac49dbb3895e0f5d7b6841115dd
Timestamp: 1722115452 Timestamp [UCT]: 2024-07-27 21:24:12 Age [y:d:h:m:s]: 00:273:23:28:05
Block: 1075098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195738 RingCT/type: yes/0
Extra: 014f960992d089fa9e35dfb8f1d992697f9ce8eac49dbb3895e0f5d7b6841115dd021100000011e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f9a6c301d80203f7d6b8ba68b6ae8dbd2dcc305e9ded0669fc00c011f346e45 0.600000000000 1547621 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": 1075108, "vin": [ { "gen": { "height": 1075098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f9a6c301d80203f7d6b8ba68b6ae8dbd2dcc305e9ded0669fc00c011f346e45" } } ], "extra": [ 1, 79, 150, 9, 146, 208, 137, 250, 158, 53, 223, 184, 241, 217, 146, 105, 127, 156, 232, 234, 196, 157, 187, 56, 149, 224, 245, 215, 182, 132, 17, 21, 221, 2, 17, 0, 0, 0, 17, 233, 20, 221, 21, 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