Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d3eb47d5328e9be98171a7e4f029d903fade6d508ebcf2f3d98cf2aa65abbcf

Tx prefix hash: 0fde9f507f69507fb608e8abc8c6ebb4b2f1979e117585a36275278593de71aa
Tx public key: 5346862d76b8ebf8e65c07e56150657f0cb587f4fa1faef3159af6dc5676b7ca
Timestamp: 1737053953 Timestamp [UCT]: 2025-01-16 18:59:13 Age [y:d:h:m:s]: 00:153:04:18:32
Block: 1198791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109175 RingCT/type: yes/0
Extra: 015346862d76b8ebf8e65c07e56150657f0cb587f4fa1faef3159af6dc5676b7ca021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a52daee9119368271794bfcfe1e630ec89cd53c5a0f6e9845de2bbc8bb7a6b23 0.600000000000 1685418 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": 1198801, "vin": [ { "gen": { "height": 1198791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a52daee9119368271794bfcfe1e630ec89cd53c5a0f6e9845de2bbc8bb7a6b23" } } ], "extra": [ 1, 83, 70, 134, 45, 118, 184, 235, 248, 230, 92, 7, 229, 97, 80, 101, 127, 12, 181, 135, 244, 250, 31, 174, 243, 21, 154, 246, 220, 86, 118, 183, 202, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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