Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd15b0a99fbfa00337d405110ea923dd8dd5a459ee9d4544568d8ca4b190451f

Tx prefix hash: 3ffbcbfeaa7c6fbf626d0af129c471bc5a494c00d22a540e57b718a20a7cbaa0
Tx public key: a63d606c32d21a3c28602df05c00ef1d8801d0b1f2eea5b7e857dbdbac208921
Timestamp: 1582036605 Timestamp [UCT]: 2020-02-18 14:36:45 Age [y:d:h:m:s]: 04:282:17:57:43
Block: 67598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1094404 RingCT/type: yes/0
Extra: 01a63d606c32d21a3c28602df05c00ef1d8801d0b1f2eea5b7e857dbdbac208921021100000004c71d3ff9000000000000000000

1 output(s) for total of 366.454932704000 dcy

stealth address amount amount idx
00: 2d4df6e8322f40468763a9e7d83310c3db8330e6f09ee053c6e92da934f6809e 366.454932704000 124483 of 0

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": 67608, "vin": [ { "gen": { "height": 67598 } } ], "vout": [ { "amount": 366454932704, "target": { "key": "2d4df6e8322f40468763a9e7d83310c3db8330e6f09ee053c6e92da934f6809e" } } ], "extra": [ 1, 166, 61, 96, 108, 50, 210, 26, 60, 40, 96, 45, 240, 92, 0, 239, 29, 136, 1, 208, 177, 242, 238, 165, 183, 232, 87, 219, 219, 172, 32, 137, 33, 2, 17, 0, 0, 0, 4, 199, 29, 63, 249, 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