Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40bf3ced6cb2d20074de9b06199613efdc1b844e2e8771320342865d66ba9ed0

Tx prefix hash: 7fb93ceb82361755dc7469b0ab852bfbf1945ae2855f6c055517622201cfea64
Tx public key: 391bcce42d56e58048d6dba81bd41e03a375630f711e45f68ba7d8f92aa72a89
Timestamp: 1705010239 Timestamp [UCT]: 2024-01-11 21:57:19 Age [y:d:h:m:s]: 01:077:13:33:15
Block: 933266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316539 RingCT/type: yes/0
Extra: 01391bcce42d56e58048d6dba81bd41e03a375630f711e45f68ba7d8f92aa72a890211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ccd03d7196b5ad9f6e3698b66b6c1a706e7a2929f519fb99bf9adbe0a8c9fa1 0.600000000000 1391228 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": 933276, "vin": [ { "gen": { "height": 933266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ccd03d7196b5ad9f6e3698b66b6c1a706e7a2929f519fb99bf9adbe0a8c9fa1" } } ], "extra": [ 1, 57, 27, 204, 228, 45, 86, 229, 128, 72, 214, 219, 168, 27, 212, 30, 3, 163, 117, 99, 15, 113, 30, 69, 246, 139, 167, 216, 249, 42, 167, 42, 137, 2, 17, 0, 0, 0, 4, 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