Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc1b54943ea4e34548612293270e3516b6395f515db73bff1e11b1c42a4af6fe

Tx prefix hash: 1a66e99fa4211247c3358889fa336eed9327d32f9e48bc9f7acfe480399482d2
Tx public key: 0bce4bae070ec18c630f850166ea8b0a546b23e21655a9f94eadaaa57f04aa60
Timestamp: 1716389928 Timestamp [UCT]: 2024-05-22 14:58:48 Age [y:d:h:m:s]: 00:357:07:52:18
Block: 1027625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255427 RingCT/type: yes/0
Extra: 010bce4bae070ec18c630f850166ea8b0a546b23e21655a9f94eadaaa57f04aa600211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37a93b2448b9932583e7d555e9cb3a3545afb25940c6e7db96cf6e2f5d741c20 0.600000000000 1495348 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": 1027635, "vin": [ { "gen": { "height": 1027625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37a93b2448b9932583e7d555e9cb3a3545afb25940c6e7db96cf6e2f5d741c20" } } ], "extra": [ 1, 11, 206, 75, 174, 7, 14, 193, 140, 99, 15, 133, 1, 102, 234, 139, 10, 84, 107, 35, 226, 22, 85, 169, 249, 78, 173, 170, 165, 127, 4, 170, 96, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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