Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21f5c5e2d4d3a57fdd7e70e7a10520c0af318e9bb84d4c5307208b2f6b594a78

Tx prefix hash: 7114162f83de6cb442cd3638ba0fe1fe1f287e6b0d32aff9cc87565020ef4ac4
Tx public key: 78d181c9824352b5e5ba4ea3f85905fa6e9e1af0f0951d37743af68c1a7f571f
Timestamp: 1726310620 Timestamp [UCT]: 2024-09-14 10:43:40 Age [y:d:h:m:s]: 00:162:11:46:32
Block: 1109869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115932 RingCT/type: yes/0
Extra: 0178d181c9824352b5e5ba4ea3f85905fa6e9e1af0f0951d37743af68c1a7f571f021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b333ba5e1df62e62e9d40383dd8e9d4ffaecc40bc92d5f3576d45c494a587f5a 0.600000000000 1588276 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": 1109879, "vin": [ { "gen": { "height": 1109869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b333ba5e1df62e62e9d40383dd8e9d4ffaecc40bc92d5f3576d45c494a587f5a" } } ], "extra": [ 1, 120, 209, 129, 201, 130, 67, 82, 181, 229, 186, 78, 163, 248, 89, 5, 250, 110, 158, 26, 240, 240, 149, 29, 55, 116, 58, 246, 140, 26, 127, 87, 31, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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