Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b9fbfdf4c3d70b35ece1698a4fb6d78c955b88607883279e3e203402c144db2

Tx prefix hash: 003cf5e16d1707d173dd07106a4d9ab8089e80c0452383c45227227a60a04d3a
Tx public key: edfe95224e1f209226e86dfe0752a1dfdacc1f735222f954aec2318a9c204f1e
Timestamp: 1679058174 Timestamp [UCT]: 2023-03-17 13:02:54 Age [y:d:h:m:s]: 01:347:02:06:49
Block: 719019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508709 RingCT/type: yes/0
Extra: 01edfe95224e1f209226e86dfe0752a1dfdacc1f735222f954aec2318a9c204f1e0211000000015029cbac000000000000000000

1 output(s) for total of 2.544435577000 dcy

stealth address amount amount idx
00: bc6eaf53cee0015e290298a6eaebd84a832bd22b16904dccbe1f9a4b86237482 2.544435577000 1163718 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": 719029, "vin": [ { "gen": { "height": 719019 } } ], "vout": [ { "amount": 2544435577, "target": { "key": "bc6eaf53cee0015e290298a6eaebd84a832bd22b16904dccbe1f9a4b86237482" } } ], "extra": [ 1, 237, 254, 149, 34, 78, 31, 32, 146, 38, 232, 109, 254, 7, 82, 161, 223, 218, 204, 31, 115, 82, 34, 249, 84, 174, 194, 49, 138, 156, 32, 79, 30, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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