Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 668bfc04f6e475927466f0d3048b24726da5fbfd46680b45e5c99771e54089fe

Tx prefix hash: 0628dc9b35093515c293de07871374757d90281cf3e8e79ac76087f35fa8f0d2
Tx public key: c6c026263e6d775a5493d89d587dc29f7be44df5aec44917718e71f229f814e2
Timestamp: 1731867436 Timestamp [UCT]: 2024-11-17 18:17:16 Age [y:d:h:m:s]: 00:185:22:24:05
Block: 1155851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132742 RingCT/type: yes/0
Extra: 01c6c026263e6d775a5493d89d587dc29f7be44df5aec44917718e71f229f814e20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 129927b4ccd0ecb774e1defd9596a1039c6d4ea40ad10e3304d1f24dfad06fb8 0.600000000000 1641470 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": 1155861, "vin": [ { "gen": { "height": 1155851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "129927b4ccd0ecb774e1defd9596a1039c6d4ea40ad10e3304d1f24dfad06fb8" } } ], "extra": [ 1, 198, 192, 38, 38, 62, 109, 119, 90, 84, 147, 216, 157, 88, 125, 194, 159, 123, 228, 77, 245, 174, 196, 73, 23, 113, 142, 113, 242, 41, 248, 20, 226, 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