Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a11d14a79a836b814a3142ec93c8e6bcea0205f3dd920a9a32f1014eefc68d7

Tx prefix hash: ce74fad131bdaa1d023d3332a3e684b75276e130767c52887c539300cdf152db
Tx public key: 231cccfe0f794ce5b5f3e2e26a7013dedd983dc5edafb6b75fa8ee857ce4e0f0
Timestamp: 1743793280 Timestamp [UCT]: 2025-04-04 19:01:20 Age [y:d:h:m:s]: 00:273:07:15:03
Block: 1254316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193132 RingCT/type: yes/0
Extra: 01231cccfe0f794ce5b5f3e2e26a7013dedd983dc5edafb6b75fa8ee857ce4e0f002110000000ba2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a60eb10e71148d3ce14301662b69c2aac4df58e09609e510e4eeea4cf8163185 0.600000000000 1741397 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": 1254326, "vin": [ { "gen": { "height": 1254316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a60eb10e71148d3ce14301662b69c2aac4df58e09609e510e4eeea4cf8163185" } } ], "extra": [ 1, 35, 28, 204, 254, 15, 121, 76, 229, 181, 243, 226, 226, 106, 112, 19, 222, 221, 152, 61, 197, 237, 175, 182, 183, 95, 168, 238, 133, 124, 228, 224, 240, 2, 17, 0, 0, 0, 11, 162, 237, 1, 107, 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