Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21e22cc0628442cdaa2457a4d31f0de97c4203f03ce6bc194dea6d1b91ec66d3

Tx prefix hash: 8fac74835d8661ee0d3548441fd5b50597ade13337152f0dcb7557a493b206e6
Tx public key: a2e95e5297629f92a5fef91845c78775fb5596fc52ef8f9d2ca0f8a9904da0e5
Timestamp: 1718079443 Timestamp [UCT]: 2024-06-11 04:17:23 Age [y:d:h:m:s]: 00:300:15:33:03
Block: 1041644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214834 RingCT/type: yes/0
Extra: 01a2e95e5297629f92a5fef91845c78775fb5596fc52ef8f9d2ca0f8a9904da0e5021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef6f4e20c1a1eb1548a1127ec372e8202f4793641459fa391df58c19cfa3823c 0.600000000000 1510369 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": 1041654, "vin": [ { "gen": { "height": 1041644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef6f4e20c1a1eb1548a1127ec372e8202f4793641459fa391df58c19cfa3823c" } } ], "extra": [ 1, 162, 233, 94, 82, 151, 98, 159, 146, 165, 254, 249, 24, 69, 199, 135, 117, 251, 85, 150, 252, 82, 239, 143, 157, 44, 160, 248, 169, 144, 77, 160, 229, 2, 17, 0, 0, 0, 2, 215, 73, 245, 17, 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