Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f70ec5a51f85263b94792f1ab4ba05b185df997f0ab96bfcf033d9a1d2d84ea8

Tx prefix hash: 4906437136cac54f84929c078065333c7072faa28e4b378676ffc834d5a493f8
Tx public key: 5866796fb5acd60f0b52c9655bce9590b2c114ddeb3a79a25b0070bc8e806c4c
Timestamp: 1765449785 Timestamp [UCT]: 2025-12-11 10:43:05 Age [y:d:h:m:s]: 00:041:13:59:33
Block: 1431224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29627 RingCT/type: yes/0
Extra: 015866796fb5acd60f0b52c9655bce9590b2c114ddeb3a79a25b0070bc8e806c4c021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41c98b369146e9aef84d870a8e65ec7489b2a00d1dfb93df33072c010fd06a35 0.600000000000 1919981 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": 1431234, "vin": [ { "gen": { "height": 1431224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41c98b369146e9aef84d870a8e65ec7489b2a00d1dfb93df33072c010fd06a35" } } ], "extra": [ 1, 88, 102, 121, 111, 181, 172, 214, 15, 11, 82, 201, 101, 91, 206, 149, 144, 178, 193, 20, 221, 235, 58, 121, 162, 91, 0, 112, 188, 142, 128, 108, 76, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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