Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c89c554e2ee33fb48cb8fe8c4234dd9bb6dc0f9a56dbf19f0cfc0f20e74951d3

Tx prefix hash: 439e3567922bf34e4b7afce190d45784e84aff5fa08f2af51538ad353b5a02db
Tx public key: 2e4e0d6fe5bb990899c86619e611dcba7c8d15ac626ad82d0991457b4cac074e
Timestamp: 1755627049 Timestamp [UCT]: 2025-08-19 18:10:49 Age [y:d:h:m:s]: 00:091:04:01:09
Block: 1350029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65066 RingCT/type: yes/0
Extra: 012e4e0d6fe5bb990899c86619e611dcba7c8d15ac626ad82d0991457b4cac074e021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f594210ca07dd70294abe92e5ed137cacc9a00a57d310757fdae4b8128dd3a6 0.600000000000 1837968 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": 1350039, "vin": [ { "gen": { "height": 1350029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f594210ca07dd70294abe92e5ed137cacc9a00a57d310757fdae4b8128dd3a6" } } ], "extra": [ 1, 46, 78, 13, 111, 229, 187, 153, 8, 153, 200, 102, 25, 230, 17, 220, 186, 124, 141, 21, 172, 98, 106, 216, 45, 9, 145, 69, 123, 76, 172, 7, 78, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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