Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6356d0b7e1da01da6fe9b109de54727ab873d5a57748b6082ae98e2fda177be

Tx prefix hash: 1014d78a5c9859b465cf23d63381a88ab19da363d4c6d0144e6404847100fd47
Tx public key: 439e977b827f0281f0727ccb83c043e7824f6b3b62f284c0a31fb4df18f68f65
Timestamp: 1747205247 Timestamp [UCT]: 2025-05-14 06:47:27 Age [y:d:h:m:s]: 00:223:10:10:47
Block: 1282577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157410 RingCT/type: yes/0
Extra: 01439e977b827f0281f0727ccb83c043e7824f6b3b62f284c0a31fb4df18f68f650211000000059f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17187222d2dd7b97498b19eeb53c2e1803aee45d2186b3eec98a27b66a705399 0.600000000000 1769984 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": 1282587, "vin": [ { "gen": { "height": 1282577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17187222d2dd7b97498b19eeb53c2e1803aee45d2186b3eec98a27b66a705399" } } ], "extra": [ 1, 67, 158, 151, 123, 130, 127, 2, 129, 240, 114, 124, 203, 131, 192, 67, 231, 130, 79, 107, 59, 98, 242, 132, 192, 163, 31, 180, 223, 24, 246, 143, 101, 2, 17, 0, 0, 0, 5, 159, 159, 230, 140, 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