Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d03243fa92f6d6efa04aa0a9e3b37f25aa0f016d596f81ea2e7408eb0e5051ea

Tx prefix hash: 218eea1d15188486460f3bc27103a638d0b17e55f4b192127e0d31f78006316f
Tx public key: fe25af0cabff05caa9d3a1d4bd37e928b08171d9bcf65414c1d35cd4aa62768f
Timestamp: 1713359566 Timestamp [UCT]: 2024-04-17 13:12:46 Age [y:d:h:m:s]: 01:027:21:54:58
Block: 1002501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280917 RingCT/type: yes/0
Extra: 01fe25af0cabff05caa9d3a1d4bd37e928b08171d9bcf65414c1d35cd4aa62768f02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d1c100fe7fe7ae9b7fa2cdfe814f82db9e7fcaf33a2f357914bc9032b4bdc09 0.600000000000 1463017 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": 1002511, "vin": [ { "gen": { "height": 1002501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d1c100fe7fe7ae9b7fa2cdfe814f82db9e7fcaf33a2f357914bc9032b4bdc09" } } ], "extra": [ 1, 254, 37, 175, 12, 171, 255, 5, 202, 169, 211, 161, 212, 189, 55, 233, 40, 176, 129, 113, 217, 188, 246, 84, 20, 193, 211, 92, 212, 170, 98, 118, 143, 2, 17, 0, 0, 0, 8, 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