Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89ec8ad3e214ff343146c57d8bc27fb5061f5168a73e8272adebe1dafb791334

Tx prefix hash: ff0533b2de82d551c1b02599ef3e7d86341b87b9a5b17ef2ca39b4a415f017ee
Tx public key: 8d1eac745a204694214c435c0f4f2ce1f924958d6db3f0ec38b25b0e67105966
Timestamp: 1736065967 Timestamp [UCT]: 2025-01-05 08:32:47 Age [y:d:h:m:s]: 00:095:14:17:06
Block: 1190624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68095 RingCT/type: yes/0
Extra: 018d1eac745a204694214c435c0f4f2ce1f924958d6db3f0ec38b25b0e6710596602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0665b00fba3354f3b0a11760e2cb6e1a93ea289a48289ff92f606153110c5b4d 0.600000000000 1677141 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": 1190634, "vin": [ { "gen": { "height": 1190624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0665b00fba3354f3b0a11760e2cb6e1a93ea289a48289ff92f606153110c5b4d" } } ], "extra": [ 1, 141, 30, 172, 116, 90, 32, 70, 148, 33, 76, 67, 92, 15, 79, 44, 225, 249, 36, 149, 141, 109, 179, 240, 236, 56, 178, 91, 14, 103, 16, 89, 102, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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