Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e879ac182ea1f1e763bbcf1b0f9de80dacc81ff7b7552fa6ab90e2b8cffab44

Tx prefix hash: 1d5b1082f17ce0af38d2332de1365573f3c033da5824f9d1c1bfe977c52f701e
Tx public key: efbf8463eb0a13eb43b053e4069d321dac57da7e1704cf8703cba70543c1d7d1
Timestamp: 1702717167 Timestamp [UCT]: 2023-12-16 08:59:27 Age [y:d:h:m:s]: 01:110:12:43:25
Block: 914273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340119 RingCT/type: yes/0
Extra: 01efbf8463eb0a13eb43b053e4069d321dac57da7e1704cf8703cba70543c1d7d10211000000014b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f226f1cff31c14da1d48166eb52f9676d9318b3331d8ae8bc4a9fb611c08e63 0.600000000000 1371567 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": 914283, "vin": [ { "gen": { "height": 914273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f226f1cff31c14da1d48166eb52f9676d9318b3331d8ae8bc4a9fb611c08e63" } } ], "extra": [ 1, 239, 191, 132, 99, 235, 10, 19, 235, 67, 176, 83, 228, 6, 157, 50, 29, 172, 87, 218, 126, 23, 4, 207, 135, 3, 203, 167, 5, 67, 193, 215, 209, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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