Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8fc1b5dce93158bd04a94190ae156d9b856bdc08b5ddbf13194d2347f03882c

Tx prefix hash: 713c3203a38b9aa0ae23921616477721657a5b02ae6b23a072cd0fcc1d390068
Tx public key: 956506d347a403083a442b1c18abe59e20f8d14b953c621287c59b90dc7c6b10
Timestamp: 1711967393 Timestamp [UCT]: 2024-04-01 10:29:53 Age [y:d:h:m:s]: 01:072:02:01:25
Block: 990929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312515 RingCT/type: yes/0
Extra: 01956506d347a403083a442b1c18abe59e20f8d14b953c621287c59b90dc7c6b1002110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c02ae118686e10ad8cccae876ce376141d90e5ed40a54c525a1e2dcaab366e6a 0.600000000000 1451261 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": 990939, "vin": [ { "gen": { "height": 990929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c02ae118686e10ad8cccae876ce376141d90e5ed40a54c525a1e2dcaab366e6a" } } ], "extra": [ 1, 149, 101, 6, 211, 71, 164, 3, 8, 58, 68, 43, 28, 24, 171, 229, 158, 32, 248, 209, 75, 149, 60, 98, 18, 135, 197, 155, 144, 220, 124, 107, 16, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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