Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5bf247220e1c4c7b0cbc3b6e3eef2a440df3fc7bad2af794888da395763e1d9

Tx prefix hash: 8994dea87144b8d8c1f52b62457771237baf5a5b2f115e1f0b42ad9e5704ffd6
Tx public key: 9ac1c86cc653eb5bb9f170279acc0231bc87d61a0d872caa5a6100a5a07c65e4
Timestamp: 1751428605 Timestamp [UCT]: 2025-07-02 03:56:45 Age [y:d:h:m:s]: 00:187:16:55:11
Block: 1316979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132464 RingCT/type: yes/0
Extra: 019ac1c86cc653eb5bb9f170279acc0231bc87d61a0d872caa5a6100a5a07c65e402110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 917b6a93b6e1125e07af829ad542d42cec9461e102ebfa3273df840558f29af4 0.600000000000 1804644 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": 1316989, "vin": [ { "gen": { "height": 1316979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "917b6a93b6e1125e07af829ad542d42cec9461e102ebfa3273df840558f29af4" } } ], "extra": [ 1, 154, 193, 200, 108, 198, 83, 235, 91, 185, 241, 112, 39, 154, 204, 2, 49, 188, 135, 214, 26, 13, 135, 44, 170, 90, 97, 0, 165, 160, 124, 101, 228, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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