Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45ea22e7e567efa35d39575d2ff52b45cd1c22c9bb933e51779ad191152b8f1b

Tx prefix hash: cf0f387963db0a6b5c86c074efc6fe5fefda52aff1e99b7d4a2d4d654aef6f32
Tx public key: b9d953a2443a5ad9ace1d7cc7b442097c1d5e394c66049a6f2601b5b42f7afe2
Timestamp: 1741984482 Timestamp [UCT]: 2025-03-14 20:34:42 Age [y:d:h:m:s]: 00:245:00:05:41
Block: 1239362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172831 RingCT/type: yes/0
Extra: 01b9d953a2443a5ad9ace1d7cc7b442097c1d5e394c66049a6f2601b5b42f7afe20211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c730511efb8e6105a9ed4e1515ed480a9ea1d3b5bf0399c902dd6cd23ca0fc64 0.600000000000 1726327 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": 1239372, "vin": [ { "gen": { "height": 1239362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c730511efb8e6105a9ed4e1515ed480a9ea1d3b5bf0399c902dd6cd23ca0fc64" } } ], "extra": [ 1, 185, 217, 83, 162, 68, 58, 90, 217, 172, 225, 215, 204, 123, 68, 32, 151, 193, 213, 227, 148, 198, 96, 73, 166, 242, 96, 27, 91, 66, 247, 175, 226, 2, 17, 0, 0, 0, 1, 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