Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea7e63dae83d5c738ac420d294efa620a20334474f9751bc97e89db94e407a5f

Tx prefix hash: bf8c54284056bf798539ef58dccfd8cac999162d8ceb65e7817a779cd4a25e49
Tx public key: ffd5c54f63e25c1891cc3d8bfe12a1c13f6b078b3907e1672063600830bb5bdc
Timestamp: 1762380710 Timestamp [UCT]: 2025-11-05 22:11:50 Age [y:d:h:m:s]: 00:046:12:27:04
Block: 1405771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33320 RingCT/type: yes/0
Extra: 01ffd5c54f63e25c1891cc3d8bfe12a1c13f6b078b3907e1672063600830bb5bdc02110000000b5dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43ba96e0b6a78e6f6749e6a87e0c0844d2faeb29c1e25f5c5b112b1358fbee57 0.600000000000 1894152 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": 1405781, "vin": [ { "gen": { "height": 1405771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43ba96e0b6a78e6f6749e6a87e0c0844d2faeb29c1e25f5c5b112b1358fbee57" } } ], "extra": [ 1, 255, 213, 197, 79, 99, 226, 92, 24, 145, 204, 61, 139, 254, 18, 161, 193, 63, 107, 7, 139, 57, 7, 225, 103, 32, 99, 96, 8, 48, 187, 91, 220, 2, 17, 0, 0, 0, 11, 93, 251, 190, 42, 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