Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c62d209d877c42d83699ae9af1b85632b5a131182853d265350db758d48ca2e

Tx prefix hash: 7254525edbde2a67162d91fe046aedd11225cef05a2247bf0c20a451c941f66a
Tx public key: afe4ad2541fbb64e209ef5ea5992bb96df649ad9c871bff4a22601d8dfb71b83
Timestamp: 1734286937 Timestamp [UCT]: 2024-12-15 18:22:17 Age [y:d:h:m:s]: 00:178:14:08:19
Block: 1175914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127417 RingCT/type: yes/0
Extra: 01afe4ad2541fbb64e209ef5ea5992bb96df649ad9c871bff4a22601d8dfb71b830211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1ccce32c978fa7863ff4decbea34a04bd5964959c38a9c5576ae8409e1535a9 0.600000000000 1662241 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": 1175924, "vin": [ { "gen": { "height": 1175914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1ccce32c978fa7863ff4decbea34a04bd5964959c38a9c5576ae8409e1535a9" } } ], "extra": [ 1, 175, 228, 173, 37, 65, 251, 182, 78, 32, 158, 245, 234, 89, 146, 187, 150, 223, 100, 154, 217, 200, 113, 191, 244, 162, 38, 1, 216, 223, 183, 27, 131, 2, 17, 0, 0, 0, 6, 31, 10, 83, 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