Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 833eb0205856cfbfe46be270f9747cab1cfebd176b7a312de2ea0970f5b6a63d

Tx prefix hash: 5e0b059cacdbdd5e692247e0f7fdf164840a5ea64d0f3e96de38a4febf2350fa
Tx public key: 418d9565aabc1f323028b2408b89f8c733079451e64cfbb5923ff4c8a25508e9
Timestamp: 1722462706 Timestamp [UCT]: 2024-07-31 21:51:46 Age [y:d:h:m:s]: 00:259:13:52:50
Block: 1077970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185428 RingCT/type: yes/0
Extra: 01418d9565aabc1f323028b2408b89f8c733079451e64cfbb5923ff4c8a25508e902110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98243a0c822ff2a96f64c7ad5befa1b53263dbf97d95a6ad90f05220f1542746 0.600000000000 1550525 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": 1077980, "vin": [ { "gen": { "height": 1077970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98243a0c822ff2a96f64c7ad5befa1b53263dbf97d95a6ad90f05220f1542746" } } ], "extra": [ 1, 65, 141, 149, 101, 170, 188, 31, 50, 48, 40, 178, 64, 139, 137, 248, 199, 51, 7, 148, 81, 230, 76, 251, 181, 146, 63, 244, 200, 162, 85, 8, 233, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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