Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0be6f640bf578fba69c147f507f055be179209b9ea9a4910520ae2185f87830b

Tx prefix hash: 11f6fd3e00048cf2df8f342c1adc9a7b7774259653df41510b82c8741ff15df3
Tx public key: 2dd94e1ab1339a6be8f7eb58dcd39a2d49fb3d0c5b962da7d22d7a6badfa4c61
Timestamp: 1698357537 Timestamp [UCT]: 2023-10-26 21:58:57 Age [y:d:h:m:s]: 01:159:23:10:30
Block: 878348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375314 RingCT/type: yes/0
Extra: 012dd94e1ab1339a6be8f7eb58dcd39a2d49fb3d0c5b962da7d22d7a6badfa4c610211000000034b8f5122000000000000000000

1 output(s) for total of 0.754516031000 dcy

stealth address amount amount idx
00: 301e19f5e690fc53855eb4fcf27ae66be1ee4dd0ce24825983e7cf6edee5cea8 0.754516031000 1333786 of 0

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": 878358, "vin": [ { "gen": { "height": 878348 } } ], "vout": [ { "amount": 754516031, "target": { "key": "301e19f5e690fc53855eb4fcf27ae66be1ee4dd0ce24825983e7cf6edee5cea8" } } ], "extra": [ 1, 45, 217, 78, 26, 177, 51, 154, 107, 232, 247, 235, 88, 220, 211, 154, 45, 73, 251, 61, 12, 91, 150, 45, 167, 210, 45, 122, 107, 173, 250, 76, 97, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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