Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5953d20440d5762c7b9caab5cebd21df6423cb2ca2d87170eb403d248bf1e3a5

Tx prefix hash: 81e6e11e073e632d0689681758ce04bb5b642842496d0003ca6dd7f7c298fbb1
Tx public key: ae508adcde6acd3ee712a81b5df5fffeac087e019640b1dbb95cac5328da49e3
Timestamp: 1709999218 Timestamp [UCT]: 2024-03-09 15:46:58 Age [y:d:h:m:s]: 01:059:19:07:35
Block: 974647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303756 RingCT/type: yes/0
Extra: 01ae508adcde6acd3ee712a81b5df5fffeac087e019640b1dbb95cac5328da49e302110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c03e17fde21043bf654dea77526d3f8518b44424580dfa2dd7608df23573e1ca 0.600000000000 1434606 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": 974657, "vin": [ { "gen": { "height": 974647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c03e17fde21043bf654dea77526d3f8518b44424580dfa2dd7608df23573e1ca" } } ], "extra": [ 1, 174, 80, 138, 220, 222, 106, 205, 62, 231, 18, 168, 27, 93, 245, 255, 254, 172, 8, 126, 1, 150, 64, 177, 219, 185, 92, 172, 83, 40, 218, 73, 227, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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