Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f34cfc0bb01fa262d2b156fc7c4f0b723ddcc84a5e9c5b71e54599d7dce27b4

Tx prefix hash: 0a68000d2b4775998b517683430f1ade03c040921600cc21eb5f6c3b99265e99
Tx public key: 80412adb3e20c0b19635af6d78a74a91e8b614eb71b2fec22e6632d04157c46b
Timestamp: 1735310373 Timestamp [UCT]: 2024-12-27 14:39:33 Age [y:d:h:m:s]: 00:078:15:46:10
Block: 1184359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56009 RingCT/type: yes/0
Extra: 0180412adb3e20c0b19635af6d78a74a91e8b614eb71b2fec22e6632d04157c46b0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ea7a2c88398b128222df56549b0f48d24fb0ea132e0970659332e2549ac58e5 0.600000000000 1670816 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": 1184369, "vin": [ { "gen": { "height": 1184359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ea7a2c88398b128222df56549b0f48d24fb0ea132e0970659332e2549ac58e5" } } ], "extra": [ 1, 128, 65, 42, 219, 62, 32, 192, 177, 150, 53, 175, 109, 120, 167, 74, 145, 232, 182, 20, 235, 113, 178, 254, 194, 46, 102, 50, 208, 65, 87, 196, 107, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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