Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd62bbd30995a091942ad6b374023a1612f9e90a1bfb43d09b4b3b2401df241c

Tx prefix hash: 8a9549ac14283ed7cabe8a564998df0aba772a6c4bc4a806e5a33f042dadff44
Tx public key: ddc5e5e49a505ccb7f81b85a009149d4350fed8cf3a5e3454059390f58982ab9
Timestamp: 1695571690 Timestamp [UCT]: 2023-09-24 16:08:10 Age [y:d:h:m:s]: 01:153:06:19:23
Block: 855230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370571 RingCT/type: yes/0
Extra: 01ddc5e5e49a505ccb7f81b85a009149d4350fed8cf3a5e3454059390f58982ab9021100000002faf35c9c000000000000000000

1 output(s) for total of 0.900052901000 dcy

stealth address amount amount idx
00: b9dc55b334e78217484764934ee203e3fc3aae6b816b1cd8b6223106936f94e6 0.900052901000 1309238 of 0

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": 855240, "vin": [ { "gen": { "height": 855230 } } ], "vout": [ { "amount": 900052901, "target": { "key": "b9dc55b334e78217484764934ee203e3fc3aae6b816b1cd8b6223106936f94e6" } } ], "extra": [ 1, 221, 197, 229, 228, 154, 80, 92, 203, 127, 129, 184, 90, 0, 145, 73, 212, 53, 15, 237, 140, 243, 165, 227, 69, 64, 89, 57, 15, 88, 152, 42, 185, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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