Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8b306ce8d7c71183bed9b88fffaf4750697e4ab41f8bd41115a1dd038040bc9

Tx prefix hash: 36589c24be860340a2c3a1e60dd717a844f3daf1e035888025cfd74030766dda
Tx public key: c5e840cdd7f3ac8f5a964df240ae3b6d304be7afb8445cfd0a9e05351898b192
Timestamp: 1712317971 Timestamp [UCT]: 2024-04-05 11:52:51 Age [y:d:h:m:s]: 01:041:15:06:35
Block: 993840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290764 RingCT/type: yes/0
Extra: 01c5e840cdd7f3ac8f5a964df240ae3b6d304be7afb8445cfd0a9e05351898b19202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11ed4d3524e1939fb5e1950d264ecb33fe7d956a0ac6c074624878a727cfa691 0.600000000000 1454228 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": 993850, "vin": [ { "gen": { "height": 993840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11ed4d3524e1939fb5e1950d264ecb33fe7d956a0ac6c074624878a727cfa691" } } ], "extra": [ 1, 197, 232, 64, 205, 215, 243, 172, 143, 90, 150, 77, 242, 64, 174, 59, 109, 48, 75, 231, 175, 184, 68, 92, 253, 10, 158, 5, 53, 24, 152, 177, 146, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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