Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b4ed6cec245179dcbe81817ebab03e468c59477460d278c800b85bb266169f5

Tx prefix hash: ec688a67eb252f7027223b9a6b045438d75585a2d8878ed6368def4d2108e17b
Tx public key: f062f1709ea4d8b657fd221bf89ce8e985242bea48f1e03cf31443d7a25e06c3
Timestamp: 1719037567 Timestamp [UCT]: 2024-06-22 06:26:07 Age [y:d:h:m:s]: 00:270:05:05:35
Block: 1049562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193110 RingCT/type: yes/0
Extra: 01f062f1709ea4d8b657fd221bf89ce8e985242bea48f1e03cf31443d7a25e06c302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34e7053c0260d9e2a47216370b58a1956efa1054663a6ab4b2e5f2f3e1fa9fe5 0.600000000000 1519661 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": 1049572, "vin": [ { "gen": { "height": 1049562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34e7053c0260d9e2a47216370b58a1956efa1054663a6ab4b2e5f2f3e1fa9fe5" } } ], "extra": [ 1, 240, 98, 241, 112, 158, 164, 216, 182, 87, 253, 34, 27, 248, 156, 232, 233, 133, 36, 43, 234, 72, 241, 224, 60, 243, 20, 67, 215, 162, 94, 6, 195, 2, 17, 0, 0, 0, 1, 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