Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ff64d80f2ab3b45478253d292bd926ae25ab2b28e2d644d46f03e7f5396c9fc

Tx prefix hash: 28cb57ddbcc690a05e8fc927f8bfca6a5404f4bf55149b59c6a07dcf3c5091dd
Tx public key: 8a402636f22503acfc77b9e92739f159d60ba13a695933fe6f6cfd19861c7d73
Timestamp: 1703814335 Timestamp [UCT]: 2023-12-29 01:45:35 Age [y:d:h:m:s]: 01:105:18:58:26
Block: 923362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336728 RingCT/type: yes/0
Extra: 018a402636f22503acfc77b9e92739f159d60ba13a695933fe6f6cfd19861c7d730211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4933dd20a9a6a5ab544bdc0696fbefa6ec95ab5f4b36c1eca3b4b62641c5f3ee 0.600000000000 1381094 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": 923372, "vin": [ { "gen": { "height": 923362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4933dd20a9a6a5ab544bdc0696fbefa6ec95ab5f4b36c1eca3b4b62641c5f3ee" } } ], "extra": [ 1, 138, 64, 38, 54, 242, 37, 3, 172, 252, 119, 185, 233, 39, 57, 241, 89, 214, 11, 161, 58, 105, 89, 51, 254, 111, 108, 253, 25, 134, 28, 125, 115, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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