Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b7004409890f3530713b01e21d891b90d8ea7f1aa68d4f08289868edb1870e4

Tx prefix hash: cd27f69be2ac44cc33d9efb74ff6e77307d710e58d8f9f702812e29b6313180c
Tx public key: 92eaa8fe5e1ff6211b86802c176a0a2882321cd8efa7d315252ceac82b591215
Timestamp: 1673043223 Timestamp [UCT]: 2023-01-06 22:13:43 Age [y:d:h:m:s]: 01:330:11:20:58
Block: 669111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497232 RingCT/type: yes/0
Extra: 0192eaa8fe5e1ff6211b86802c176a0a2882321cd8efa7d315252ceac82b59121502110000000252542ceb000000000000000000

1 output(s) for total of 3.723552267000 dcy

stealth address amount amount idx
00: 4667613afe2c911459ad33c6c84448a2126cb57a16026fc0b9e5ca9f4e522f17 3.723552267000 1110412 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": 669121, "vin": [ { "gen": { "height": 669111 } } ], "vout": [ { "amount": 3723552267, "target": { "key": "4667613afe2c911459ad33c6c84448a2126cb57a16026fc0b9e5ca9f4e522f17" } } ], "extra": [ 1, 146, 234, 168, 254, 94, 31, 246, 33, 27, 134, 128, 44, 23, 106, 10, 40, 130, 50, 28, 216, 239, 167, 211, 21, 37, 44, 234, 200, 43, 89, 18, 21, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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