Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e304ad7f7f9178383c742962b416a7b4fdc478ac60046559cc358c7d5a105108

Tx prefix hash: 236de9efc420ce3160fb17a37e0f979c41ae5723988dd43c227a8fd6d76b9e10
Tx public key: dd66ce0df3beb6324bb50493ebc87827b945ec0fa5007d4bf4278a27c5a67b40
Timestamp: 1720512950 Timestamp [UCT]: 2024-07-09 08:15:50 Age [y:d:h:m:s]: 00:345:22:07:21
Block: 1061814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247067 RingCT/type: yes/0
Extra: 01dd66ce0df3beb6324bb50493ebc87827b945ec0fa5007d4bf4278a27c5a67b4002110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a06c837c32fdb03d2ca3f33ea519a1dc5f2daea268025031bebda472c36e68d 0.600000000000 1532309 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": 1061824, "vin": [ { "gen": { "height": 1061814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a06c837c32fdb03d2ca3f33ea519a1dc5f2daea268025031bebda472c36e68d" } } ], "extra": [ 1, 221, 102, 206, 13, 243, 190, 182, 50, 75, 181, 4, 147, 235, 200, 120, 39, 185, 69, 236, 15, 165, 0, 125, 75, 244, 39, 138, 39, 197, 166, 123, 64, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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