Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f2089bfe8ca6b363881cd02c1b42b4a3a4c00fed675f2f745bb18f4d0173f57

Tx prefix hash: 46739527dcf5f9b5afd202ba71286b3b746624f966df680f3565cdad6d81379f
Tx public key: a16f5360c3f34b3189ce9ebdffcc5d6dcee0631e08371a5363aa4676d626af45
Timestamp: 1734742417 Timestamp [UCT]: 2024-12-21 00:53:37 Age [y:d:h:m:s]: 00:178:20:36:24
Block: 1179685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127522 RingCT/type: yes/0
Extra: 01a16f5360c3f34b3189ce9ebdffcc5d6dcee0631e08371a5363aa4676d626af450211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89bed9858f259ed5e06643e21853f66d36372dbf11fc8ba393809fd1fd516cd9 0.600000000000 1666084 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": 1179695, "vin": [ { "gen": { "height": 1179685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89bed9858f259ed5e06643e21853f66d36372dbf11fc8ba393809fd1fd516cd9" } } ], "extra": [ 1, 161, 111, 83, 96, 195, 243, 75, 49, 137, 206, 158, 189, 255, 204, 93, 109, 206, 224, 99, 30, 8, 55, 26, 83, 99, 170, 70, 118, 214, 38, 175, 69, 2, 17, 0, 0, 0, 7, 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