Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0c115bb1a7835b29edbe6d373b71d9733513d0394b25e40100b4ffde16f04c8

Tx prefix hash: 4e7b3323481ca32469753bc0b7fbc6b0c0bbfe4d75fac8453af0770032d5b1f1
Tx public key: 399ad6e4c674d7a4ccb5d5f8b5dc4210f3cb9ccc7f840f6b38b9ae9029db3357
Timestamp: 1737361447 Timestamp [UCT]: 2025-01-20 08:24:07 Age [y:d:h:m:s]: 00:330:15:56:42
Block: 1201289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233921 RingCT/type: yes/0
Extra: 01399ad6e4c674d7a4ccb5d5f8b5dc4210f3cb9ccc7f840f6b38b9ae9029db33570211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fc40c552baac2064daad40e4e92e32cf2668d2287665de934a6565b203c571b 0.600000000000 1687938 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": 1201299, "vin": [ { "gen": { "height": 1201289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fc40c552baac2064daad40e4e92e32cf2668d2287665de934a6565b203c571b" } } ], "extra": [ 1, 57, 154, 214, 228, 198, 116, 215, 164, 204, 181, 213, 248, 181, 220, 66, 16, 243, 203, 156, 204, 127, 132, 15, 107, 56, 185, 174, 144, 41, 219, 51, 87, 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