Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4721a35a0a31a79d1704f4a5d2ff4d023a97c5ad2a924d50fc22925e4b4a81c

Tx prefix hash: b1c69b90f8e90a42707d59e87e7e953a0eb5b7b779130cb4b2d2e95fd864195c
Tx public key: 7bcba4c63ad94bce47ba0dd4e58a0f5d33a30bcd11e6c11efa811690c9242f34
Timestamp: 1735763356 Timestamp [UCT]: 2025-01-01 20:29:16 Age [y:d:h:m:s]: 00:090:05:51:45
Block: 1188103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64276 RingCT/type: yes/0
Extra: 017bcba4c63ad94bce47ba0dd4e58a0f5d33a30bcd11e6c11efa811690c9242f340211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e8a41b34a135c8ea87baad6644dc78c3d25824b94649962ef4c26c7bb4d6754 0.600000000000 1674602 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": 1188113, "vin": [ { "gen": { "height": 1188103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e8a41b34a135c8ea87baad6644dc78c3d25824b94649962ef4c26c7bb4d6754" } } ], "extra": [ 1, 123, 203, 164, 198, 58, 217, 75, 206, 71, 186, 13, 212, 229, 138, 15, 93, 51, 163, 11, 205, 17, 230, 193, 30, 250, 129, 22, 144, 201, 36, 47, 52, 2, 17, 0, 0, 0, 2, 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