Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08d761ad3e4681ea9b168838700334cae5d26eb34b857feaa41f666c5ddb8105

Tx prefix hash: 073d8e109a042fe714d76942af81f9b17ceaf398fb1f1f657c63e4be72678167
Tx public key: 5837dbc4f4fe0ee33f01e986c8175429bddd3ad5e676a234e6a22e96e797cd2e
Timestamp: 1707256069 Timestamp [UCT]: 2024-02-06 21:47:49 Age [y:d:h:m:s]: 01:287:20:03:11
Block: 951888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464509 RingCT/type: yes/0
Extra: 015837dbc4f4fe0ee33f01e986c8175429bddd3ad5e676a234e6a22e96e797cd2e021100000001ec57b234000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e1e354333f548f8b66569cd14cfdf5a9fa8b3730b6b79f34458f6b6216d1853 0.600000000000 1410730 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": 951898, "vin": [ { "gen": { "height": 951888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e1e354333f548f8b66569cd14cfdf5a9fa8b3730b6b79f34458f6b6216d1853" } } ], "extra": [ 1, 88, 55, 219, 196, 244, 254, 14, 227, 63, 1, 233, 134, 200, 23, 84, 41, 189, 221, 58, 213, 230, 118, 162, 52, 230, 162, 46, 150, 231, 151, 205, 46, 2, 17, 0, 0, 0, 1, 236, 87, 178, 52, 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