Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c52f839f3c41144d752573d06f8a8dd108ea31db95c3c5b9546eef56da37ab34

Tx prefix hash: 0a8b38283d67834a6d6ac6adc8947af28d46f4b2c91a608ca034d0553f94d95a
Tx public key: 14ff640296a214a9c807f593c62d0b5f855394642c8d6f2f2265de6c356bda91
Timestamp: 1745140468 Timestamp [UCT]: 2025-04-20 09:14:28 Age [y:d:h:m:s]: 00:206:01:56:18
Block: 1265470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145003 RingCT/type: yes/0
Extra: 0114ff640296a214a9c807f593c62d0b5f855394642c8d6f2f2265de6c356bda91021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12c1605eade8d0b7d7d39284687c8ac4196ad3999f5cf233b9a0502fe2b2642c 0.600000000000 1752679 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": 1265480, "vin": [ { "gen": { "height": 1265470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12c1605eade8d0b7d7d39284687c8ac4196ad3999f5cf233b9a0502fe2b2642c" } } ], "extra": [ 1, 20, 255, 100, 2, 150, 162, 20, 169, 200, 7, 245, 147, 198, 45, 11, 95, 133, 83, 148, 100, 44, 141, 111, 47, 34, 101, 222, 108, 53, 107, 218, 145, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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