Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a092daf06b7fbc111a1bcccf5f82ccc8b6234b350d9d7b3c2f4ec9ea443787b

Tx prefix hash: 244058557382c69baaf62b43e67fa5fa7c2509c0845107c4697d5dfedf1b5090
Tx public key: 35cf37977e95641cc1b91dc532b3751026878359a771aecc5588d5e51fb8665f
Timestamp: 1719691600 Timestamp [UCT]: 2024-06-29 20:06:40 Age [y:d:h:m:s]: 00:355:12:52:45
Block: 1054988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253953 RingCT/type: yes/0
Extra: 0135cf37977e95641cc1b91dc532b3751026878359a771aecc5588d5e51fb8665f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b40c89b8333843e9da721dcab97c18c9f5ebea45a9c34b6a97e3f5a2c51ca9b7 0.600000000000 1525379 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": 1054998, "vin": [ { "gen": { "height": 1054988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b40c89b8333843e9da721dcab97c18c9f5ebea45a9c34b6a97e3f5a2c51ca9b7" } } ], "extra": [ 1, 53, 207, 55, 151, 126, 149, 100, 28, 193, 185, 29, 197, 50, 179, 117, 16, 38, 135, 131, 89, 167, 113, 174, 204, 85, 136, 213, 229, 31, 184, 102, 95, 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