Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f9705b908ef58655b29f9716799c6d4d48e053af043d9e5dc824b2749e1edc9

Tx prefix hash: f1120327ba80fe5fb3a3bdef9868cf216ebfe723621be7896c020c215a72ac26
Tx public key: c8dcc1aa859cde28a6f9a1eb5dcff4e2c26df6269a12e8493c692074b74667c8
Timestamp: 1719544603 Timestamp [UCT]: 2024-06-28 03:16:43 Age [y:d:h:m:s]: 00:333:15:54:24
Block: 1053776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238461 RingCT/type: yes/0
Extra: 01c8dcc1aa859cde28a6f9a1eb5dcff4e2c26df6269a12e8493c692074b74667c80211000000020cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c178ad0f4163706657ce350ef77a69898a032279d2df3ee80a206ac2536b116 0.600000000000 1524127 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": 1053786, "vin": [ { "gen": { "height": 1053776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c178ad0f4163706657ce350ef77a69898a032279d2df3ee80a206ac2536b116" } } ], "extra": [ 1, 200, 220, 193, 170, 133, 156, 222, 40, 166, 249, 161, 235, 93, 207, 244, 226, 194, 109, 246, 38, 154, 18, 232, 73, 60, 105, 32, 116, 183, 70, 103, 200, 2, 17, 0, 0, 0, 2, 12, 206, 6, 54, 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