Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60b930b02cf3d1f55e54e9d4dbc9ec6bed33f1af6e2464549169f5fd198bb146

Tx prefix hash: 99c2402ffc5e839a43b387c27f49fc7cc0341fb67417d99181e08db647ccb187
Tx public key: ebc068e85fbc7d67b0aa752651c73042c9f62441306c51a47b93949e50e34029
Timestamp: 1708560504 Timestamp [UCT]: 2024-02-22 00:08:24 Age [y:d:h:m:s]: 01:117:01:53:26
Block: 962719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344620 RingCT/type: yes/0
Extra: 01ebc068e85fbc7d67b0aa752651c73042c9f62441306c51a47b93949e50e340290211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4a9f2d321420a21249b4604e29937ad5095c862522fc6aa2f0ff9016efa95a3 0.600000000000 1422402 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": 962729, "vin": [ { "gen": { "height": 962719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4a9f2d321420a21249b4604e29937ad5095c862522fc6aa2f0ff9016efa95a3" } } ], "extra": [ 1, 235, 192, 104, 232, 95, 188, 125, 103, 176, 170, 117, 38, 81, 199, 48, 66, 201, 246, 36, 65, 48, 108, 81, 164, 123, 147, 148, 158, 80, 227, 64, 41, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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